Update release docs: TLS has shipped - #17
Merged
Merged
Conversation
midge.readme and userdocs/index.md still said TLS was "planned for future releases" - stale since the AmiSSL transport landed and shipped in mqtt.library/mqtt_pub/mqtt_sub. Both now describe it as available (mco_TLS/TLS-TLSINSECORE, AmiSSL required separately, CPU-speed caveat). Installation.md gets a new "Installing AmiSSL (needed for TLS)" section alongside the existing mqtt.library install step - the missing piece a release user would actually need to discover TLS is usable at all. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QWq1CRLCQy9AaD9UtLRSM9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
midge.readmeanduserdocs/index.mdstill said TLS was "planned for future releases" - stale since the AmiSSL transport shipped in mqtt.library/mqtt_pub/mqtt_sub (Phase 3: TLS support via AmiSSL #3). Both now describe it as available, with the AmiSSL-must-be-installed-separately and CPU-speed caveats carried over.userdocs/Installation.md, mirroring the existing mqtt.library install-step section - the missing piece a release user needs to actually discover/use TLS.Test plan
mkdocs build --strictpasses with no warnings (anchor links resolve).python3 tools/docs2guide.py userdocs ...converts cleanly (5 nodes, no errors).🤖 Generated with Claude Code
https://claude.ai/code/session_01QWq1CRLCQy9AaD9UtLRSM9